System and method for intelligent service assurance in network management

ABSTRACT

Systems and methods for intelligent service assurance testing provided herein include receiving network infrastructure information relating to a network, receiving one or more service assurance testing parameters, determining a test schedule of one or more service assurance tests for service assurance testing of the network, the test schedule being based at least in part on the network infrastructure information and the one or more service assurance testing parameters, and deploying the one or more service assurance tests on one or more devices of the network according to the test schedule.

FIELD OF THE INVENTION

The invention relates to intelligent provisioning and deployment ofservice assurance testing in computing networks using networkinfrastructure information.

BACKGROUND OF THE INVENTION

Service assurance techniques have a significant role in the managementof large Enterprise and Service Provider Networks. There are a number ofstandard as well as vendor proprietary techniques to choose from toaccomplish tasks like connectivity testing, response time analysis, pathmonitoring, etc. One problem is that testing is relatively difficult andresource intensive to deploy and can cause scalability problems if testsare not designed correctly. One example of this is connectivity testingbetween sites in an enterprise network. Testing with even a relativelymodest number of sites (like 100) can create almost 10,000 tests in asingle poll cycle when a full mesh test architecture is used. One of thechallenges of this situation is that most tests are created by hand—oneat a time. Although network management systems may automate some aspectof test creation and analysis, there is still a significant scalingproblem.

Many tests are, deployed either one at a time or “en masse,” withneither approach providing optimal coverage. The process of creating onetest at a time may never yield appropriate coverage, while bulk creationmay waste resources by provisioning tests indiscriminately.

Another concern in deploying service assurance testing is thepossibility of test scale impacting network operations and performancenegatively. Other difficulties may also exist.

Thus, provisioning and deployment of optimal testing that providesappropriate coverage for the environment, the equipment, performancegoals and/or assurance level required by the enterprise or user isdesirable.

SUMMARY

The invention provides systems and methods for providing serviceassurance testing of a computing network (e.g., an enterprise network, aservice provider network, and/or other computer network). Currentnetwork management solutions (e.g., Spectrum® Infrastructure Manageroffered by CA, Inc., eHealth® performance manager offered by CA, Inc.,or other applications) may enable a user to configure and deploy serviceassurance tests. However, this process typically involves one or moremanual steps and does not enable robust information regarding thenetwork to inform testing design and deployment. The systems and methodsof the invention bring much more information to testing provisioning anddeployment and relieve users of steps in making, configuring, anddeploying each test.

A system for service assurance may include a network managementcomponent executing a network management application. The networkmanagement application may be or include a computer application (orplurality of applications capable of communicating with one another)having one or more modules thereon.

The one or more modules may include instructions for receiving networkinfrastructure information relating to the network, receiving one ormore service assurance testing parameters, determining a test scheduleof one or more service assurance tests for service assurance testing ofthe network, deploying the one or more service assurance tests on one ormore devices of the computer network according to the test schedule,receiving results of the one or more service assurance tests, generatingone or more reports using the received results, and/or to perform otherfeatures or functions.

In some implementations, network infrastructure information may includeinformation relating to network topology, information regarding networktraffic patterns, network traffic class information, applicationdeployment information, service deployment information, networkingtechnology information, and/or other information.

In some implementations, the invention provides a method for improvedservice assurance testing. In some implementations, the invention mayinclude a tangible computer readable storage media having computer orprocessor-executable instructions thereon, that when executed by one ormore processing devices, may configure the one or more processingdevices to perform one or more of the features and functions describedherein.

Various other objects, features, and advantages of the invention will beapparent through the detailed description and the drawings attachedhereto. It is also to be understood that both the foregoing generaldescription and the following detailed description are exemplary and notrestrictive of the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of an environment that includes a systemfor performing service assurance testing, according to variousimplementations of the invention.

FIG. 2 illustrates an example of a process for performing serviceassurance testing, according to various implementations of theinvention.

DETAILED DESCRIPTION OF THE INVENTION

The invention provides systems and methods for providing serviceassurance testing of a computing network. FIG. 1 illustrates anenvironment 100, which is an example of an environment in which a systemfor providing service assurance testing for a network resides.Environment 100 may include system 101, which is an example of a systemfor providing service assurance testing for a network. System 101 mayinclude a network management component 103, which may run or operate anetwork management application 105. Network management component 103 maybe or include one or more servers or other computing devices having oneor more processors that are configurable by computer readable/executableinstructions for performing one or more features and functions,including those disclosed herein. Network management application 105 maybe or include a computer application (or plurality of applicationscapable of communicating with one another) having one or more modules107 a-107 n or computer executable instructions thereon that configurethe one or more processors of network management component 103 toperform one or more of the service assurance testing features andfunctions described herein, and/or other functions.

In some implementations, modules 107 a-107 n may include computerexecutable instructions embodied on computer readable storage media suchas, for example, one or more disks, tapes, non-volatile memory, harddisks, or other computer readable storage media (e.g., magnetic media,digital media, or other media). In some implementations modules 107a-107 n may be implemented across multiple applications and/or deviceswithin environment 100 to perform the service assurance testing featuresand functions herein and/or other features and functions.

In some implementations, modules 107 a-107 n may include instructionscausing the one or more processors of network management application 103to receive network infrastructure information relating to the network,receive one or more service assurance testing parameters, determine atest schedule of one or more service assurance tests for serviceassurance testing of the network, the test schedule being based at leastin part on the network infrastructure information and the one or moreservice assurance testing parameters, calculate cost information for agiven testing schedule based on received/derived information, deploy theone or more service assurance tests on one or more devices of thecomputer network according to the test schedule, receive results of theone or more service assurance tests, generate one or more reports usingthe received results, and/or to perform other features or functions.

In some implementations, some or all of modules 107 a-107 n may be partof or may operate in conjunction with Spectrum® Infrastructure Manageroffered by CA, Inc., which is an integrated management solution forbusiness service management, fault isolation and root cause analysis,and network configuration management that enables enterprises,government agencies and service providers to avoid the cost and risk ofservice delivery failure. In some implementations, network managementapplication 105 may be, may be part of, or may interact with (e.g.,send/receive information) the Spectrum® infrastructure manager. In someimplementations, some or all of modules 107 a-107 n may be part of ormay operate in conjunction with eHealth® performance manager offered byCA, Inc., which is a performance management solution that enablesmanagement of a diverse collection of devices from numerous vendors,isolates the source of performance degradation, minimizes recurringexpenses, and provides detailed and executive level historicalreporting. In some implementations, network management application 105may be, may be part of, or may interact with (e.g., send/receiveinformation) the eHealth® performance manager. In some implementations,modules 107 a-107 n and/or the features and functions thereof may bepart of and/or operate in conjunction with other network managementapplications.

In some implementations, environment 100 may include one or more networkelements 109, which may include one or more servers, desktops, laptops,workstations, wireless devices (e.g., smartphones, personal digitalassistants, etc.), routers, switches, or other network devices. One ormore network elements 109 may be portioned into one or more sections orportions of a network operating in environment 100. FIG. 1 illustratesnetwork portions 111 a, 111 b, and 111 c, which are examples of specificportions of a network having one or more network infrastructurecharacteristics. Network infrastructure characteristics may include anyinformation relating to the structure or internal workings of a network.

In some implementations, a network infrastructure characteristic mayinclude information relating to network topology. Network topologyinformation may include information regarding how network devices arephysically structured relative to one another (approaches forinterconnecting network devices). For example, the particular locationand configuration of routers, switches, servers, workstations and/orother network devices comprise network topology information. In someimplementations, network topology information may be used to construct amap of the network or a specific portion thereof. Knowledge of networktopology may be useful in service assurance testing as awareness of agiven topology may enable selection and/or configuration of serviceassurance tests that are more useful with the given topology. Likewise,knowledge of the given topology may enable avoidance of deployment ofless useful service assurance tests to networks or portions thereofhaving the given topology.

For example, if a given network or portion thereof is known to have a“hub-and-spoke” topology (e.g., portion 111 b of FIG. 1) where trafficfrom all spokes must traverse a hub, full mesh testing between all thespokes (e.g., testing connectivity between all pairs of individualdevices in the hub-and-spoke system) is not necessary, as only testingof connectivity of each spoke to the hub is sufficient. Other topologyinformation may be used to make other types of service assurance testingdeterminations. For example, in some instances, an overlapping VPN(virtual private network) topology may be employed, whereinmembers/devices participate in more than one VPN. Given this informationregarding a multiple VPN topology, connectivity testing betweendevices/members in multiple groups may be performed. In anotherinstance, a “tunneled traffic” topology may be employed in a network,which may present service assurance testing challenges due to the needfor testing of both the “inner” and “outer” traffic entities. However,knowledge of this tunneled traffic topology enables the proper testingto be done.

In some implementations, network topology may be determined using Layer2 infrastructure, Layer 3 infrastructure, VRF tables, route analyticstools, and/or other information. As described herein, this topologyinformation may be used more efficient or optimized tests. It should benoted that the concept of connectivity may exist at many differentlevels. For example, in some layered networks, entities/devices whichare “connected” at one level may not actually be connected (or providingservice) at the next higher level. The complex nature of multi-layerednetwork structures gives a multi-dimensional nature to the problem ofefficient service assurance testing. Each “layer” may have its ownService Assurance tools and policies. These tools must be appliedappropriately to give complete coverage. As such, multiple layers shouldbe queried as needed to determine the relevant topology in a givenportion of network in which testing is desired.

In some implementations, network infrastructure characteristics mayinclude information regarding network traffic patterns. Traffic patterninformation may include information regarding how many packets (or otherinformation) flow through a network and/or specific portions of thenetwork, whether the packets (or other information) are flowing to orfrom a particular portion of a network, the source and/or destination ofpackets (or other information flowing through a network), descriptivecharacteristics of packets (or other information) flowing through thenetwork, and/or other network traffic-related information. In someimplementations, traffic pattern information may include informationrelating to engineered traffic flow of network communication paths. Insome implementations, network traffic information may be useful inservice assurance testing as awareness of traffic patterns may enableselection and/or configuration of service assurance tests that are moreuseful or efficient. Likewise, knowledge of traffic flow may enableavoidance of deployment of less useful service assurance tests orcritical tests to given portions of a network. For example, areas withhigh traffic may be tested more frequently and/or intensively, whereaslow traffic areas may not be scrutinized/tested as much.

In some implementations, traffic pattern or path information may beobtained from tools like Netflow/Jflow collectors and/or monitoringinterface utilization (e.g., to find heavily used links).

Another example includes an enterprise network where many sitescommunicate back to a corporate headquarters (but not necessarily siteto site). While this is similar in concept to a spoke and hubenvironment, it is potentially more difficult to actually recognize. Inthis example, traffic information may be used to identify trafficpatterns indicating “corporate hubs” that may host enterprise-wideservices (e.g., databases, Internet access, email filtering, callmanagement, etc.) Thus, service assurance tests may be focused on thesecorporate hubs, rather than on other, less-crucial areas. Other types ofnetwork infrastructure information (e.g., traffic class,service-awareness, application deployment awareness), may be used toidentify these types of hubs, but the above-described trafficinformation may provide a less knowledge intensive way to make suchidentifications, may provide initial information as to “where to look,”and/or may be used in conjunction with other infrastructure informationto identify these types of hubs. Similarly, in some implementations, itshould be understood that any one of the types of infrastructureinformation described herein (or other infrastructure information) maybe used in conjunction with or in place of other types of infrastructureinformation for the purposes of designing and/or implementingintelligent service assurance testing.

In some implementations, network infrastructure characteristics mayinclude network traffic class information. Network traffic classinformation may include information relating to any classification ofunits of network traffic. For example, packets travelling across anetwork may be classified based on priority (e.g., from high to lowpriority). Priority classification may include quality of service(QOS)/class of service (COS) determinations and may ultimately be tiedto the functions and services that a given portion of network supports.Traffic class information may be used to provide moreeffective/efficient/optimized testing of a network or portions thereof.For example, a portion of a network carrying packets classified as highpriority because they relate to a service guaranteed at a high QOS(e.g., voice over IP [VoIP] services) may receive additional and/orexpedited testing, as failure these portions of a network would becostly and/or extremely disruptive. In addition, it may benecessary/desirable to perform testing at the traffic class the serviceis actually being delivered on. For example, it would not make sense totest at high QoS levels if no active service was deployed at this levelin an area of the network. Additionally, testing a portion of a networkon which high QoS packets travel may carry a higher “cost” than testingelsewhere, as the testing may disrupt service. Thus, testing on thishigh QoS area may be provisioned more judiciously than testingelsewhere.

In some implementations, network infrastructure characteristics mayinclude application deployment information. Application deploymentinformation may include information relating to softwareinstalled/running on certain portions of a network. This softwaredeployment information may be used to provide moreeffective/efficient/optimized testing of a network or portions thereof.For example, knowledge of the devices on which critical software isinstalled may be used to provide more intensive testing on the portionsof the network that include these devices. Furthermore, knowledge ofwhat software is deployed where may assist in specifically tailoringtesting for portions of network having specific software deployedthereon.

In some implementations, network infrastructure characteristics includeservice deployment information. Service deployment information mayinclude information relating to services supported on a given network.Services may be supported by one or more devices within the network andmay be accessible by and/or exchange data with numerous other deviceswithin the network and outside of the network. Service deploymentinformation may be used to provide “environment aware” or “serviceaware” testing. Service aware testing includes testing wherein the teststhat are generated depend on the services discovered in the network. Forexample, in networks carrying services involving voice or video traffic,tests unique to these services are provisioned. These tests are deployedonly in portions of the network carrying voice or video traffic. Thisapproach eases the burden on creation and deployment tests in thenetwork and improves useful capacity by focusing tests where they areneeded most.

In some implementations, network topology information, traffic patterninformation, traffic class information, application deploymentinformation, service deployment information, and/or other informationmay be referred to as “detailed topology information,” which may be usedas network infrastructure characteristics as discussed herein. In someimplementations, traffic pattern/path information and traffic classinformation may be referred to as information relating to traffic withinthe network or “network traffic information.”

In some implementations a map or “topological map” of a network or oneor more portions thereof may be constructed. In some implementations themap may include information relating to the physicaltopology/configuration of the network (or portion), traffic patterninformation, traffic class information, application deploymentinformation, service deployment information, networking technologyinformation (described below), and/or other information. The map mayillustrate where, and/or on what devices/portions within the network,certain traffic patterns/volumes occur, certain traffic classes travel,certain applications or services are deployed, certain networkingtechnologies exist, and/or other information. The constructed map and/orany portion of the information shown therein may be used to implementimproved/intelligent service assurance testing.

In some implementations, network infrastructure characteristics mayinclude networking technology information. Networking technologyinformation may include information relating to one or more of signalingtechnologies used in a given portion of a network, a propagation mediumused in a given portion of a network, standards used in a given portionof a network, protocol used in a given portion of a network and/or otherinformation relating to how information/data is propagated through agiven portion of the network. Networking technologies in a network or agiven portion of a network may determine what kinds of tests aredeployed. Nearly every technology has its own set of connectivity andfault management tools. For example, multi-protocol label switching(MPLS) technology utilizes MPLS Ping & Trace, while L3 MPLS VPNs utilizeVRF Ping & Trace. In pure ethernet networks IEEE 802.1ag providesConnectivity Fault Management (CFM) and 803.3ah provides Ethernet LinkOAM (operations administration and management). In pure internetprotocol (IP) networks, tests such as “ping” and “traceroute” may bedeployed between key endpoints in the network.

In some implementations, certain network infrastructure characteristicsmay apply to only certain defined portions of a given network. Forexample, as illustrated in FIG. 1, one or more of network portions 111a, 111 b, and/or 111 c may have different network structures, may havedifferent traffic patterns, may carry traffic having differentclassifications, may have different applications installed thereon, maysupport different services, and/or may utilize different networkingtechnologies. In some instances, some or all network infrastructurecharacteristics may be applicable across various portions of or even anentire network.

In some implementations environment 100 may be or include the networkbeing managed. In some implementations environment 100 may includenumerous networks or portions thereof and/or may also include apublically accessible network 113 such as, for example, the Internet andone or more devices 115 accessible over network 113.

In some implementations, the invention provides a method forimproved/intelligent service assurance testing. FIG. 2 illustrates aprocess 200, which is an example of a process for providingimproved/intelligent service assurance testing. In some implementations,process 200 may be performed by one or more processors configured bycomputer executable instructions for performing a plurality ofoperations (e.g., the operations of process 200).

Process 200 includes an operation 201, wherein network infrastructureinformation (e.g., information relating to network infrastructurecharacteristics) relating to a network is received. As discussed above,network infrastructure information/characteristics may include networkstructure information, traffic pattern/path information, traffic classinformation, application deployment information, service deploymentinformation network topology information, networking technologyinformation, and/or other information.

In an operation 203, one or more service assurance testing parametersmay be received. Testing parameters may include information relating totesting of the network such as, for example, a desired portion of thenetwork to be tested, desired frequency or timetable of testing, desiredtype of tests or testing (e.g., connectivity testing, performancetesting, etc.), and/or other testing related information. Testscheduling and frequency are important parameters in the FaultManagement value of Service Assurance Tests. While more frequent testingprovides the ability to identify faults more quickly, it significantlyimpacts the resources required to perform testing. In someimplementations, an optimal configuration of tests should consider the“costs” of executing the tests. As used herein, the term cost includesany burden imposed on the network or a portion thereof (i.e., “resourcecosts” such as, for example, CPU and/or memory utilization, networkbandwidth utilization, etc.) or expenditure that must be made(including, but not limited to financial expenditures and/or equivalentrepresentations thereof) as a result of performing a given test (e.g.,to maintain a given QoS for a service that is disrupted by a test, anenterprise may expend certain man-hours, physical inventory, and/ormonies). The costs to the Network Management System, device and serviceunder test as well as the network make certain levels of testing costprohibitive. As such, in some aspects, the invention described hereinidentifies critical areas where enhanced testing is both beneficial andwarranted.

In some implementations, the network infrastructure information and/ortesting parameters may be received by a network management application(e.g., application 105) and/or one or more modules thereof (e.g.,modules 107 a-107 n). In an operation 205, the management application ormodules may determine a test schedule of one or more service assurancetests for service assurance testing of the network. The test schedulemay be based, at least in part, on the network infrastructureinformation and the one or more service assurance testing parameters. Asdiscussed herein, provisioning tests may have a net cost to certaindevices, services, and/or the network as a whole. As such, in someimplementations, determination of the testing schedule may include adetermination of these costs and a decision as to what tests to deploy,where they are to be deployed, when to deploy the tests, whether todeploy the tests at all, etc. In some implementations, cost informationmay be input as a service assurance test parameter. Information used todetermine “costs” of testing may be derived from network infrastructurecharacteristics/information, received testing parameters, and/or otherinformation (e.g., a lookup table, matrix, or other correlation enginethat utilizes factual information gathered about the networkinfrastructure and applies the received testing parameters to provide aprediction, estimate, or determination of a cost metric). This costinformation (which may be qualitative or quantitative) may then be usedto either provision the tests (i.e., determine the schedule) accordingto the received testing parameters (i.e., if the received parameters donot pose a problem re: cost to the network), to provision the testsaccording to modified parameters (i.e., modified by the networkmanagement application or its modules to optimally reduce the costs tothe network), and/or to suggest testing parameters (or multiple optionstherefore) for approval or selection by a user/administrator.Determinations re: formulating a testing schedule in light of costinformation may, in some implementations, essentially be a cost-benefitanalysis or cost-necessity analysis. Other schemes may be implementedregarding how cost information is used in determining testing schedules.

In an operation 207, one or more service assurance tests may be deployedby the network management application or its constituent modules on oneor more devices of the computer network according to the determined testschedule.

In an operation 209, the management application and/or modules mayreceive results of the deployed tests. These results may include whetheror not a given network device is responsive or in communication with agiven portion of the network (e.g., connectivity testing) and/or anymetrics received as a result of performance or connectivity testing(e.g., response time, computation time, etc.). The received results maythen be examined to make calculations and/or draw conclusions from theseresults. For example, if certain devices are determined to not be incommunication with a given portion of the network, an alarm may betriggered notifying an administrator or other entity of the need for arepair or a workaround. In another example, if a given process supportedby the network is determined to be performing at an unacceptable rate(e.g., as determined by one or more performance tests), remediativemeasures may be prescribed to increate the performance rate.

In an operation 211, one or more reports may be generated using thereceived testing results and/or any conclusions/determinations derivedtherefrom. In some implementations, the report may be sent to one ormore recipients (e.g., administrators, managers, etc.) electronically orotherwise communicated to recipients. In some implementations, anyactions deemed necessary or advisable from the results may be performedto assure desired service/performance from the network.

In some implementations, the invention may include a tangible computerreadable storage media having computer or processor-executableinstructions thereon that, when executed by one or more processingdevices, may configure the one or more processing devices to perform oneor more of the features and functions described herein.

Those of ordinary skill in the art will appreciate that the systemsdescribed herein are examples and that the system of the invention mayinclude more or less of the described components/elements and that thefeatures and functions described herein may be performed by componentsdifferent from those described herein. In some implementations thefunctions of certain components and/or may be combined. Those ofordinary skill in the art will also appreciate that themethods/processes described herein are examples and thatmethod/processes according to the invention may have more or feweroperations than described above, that the operations may be performed ina different order than described above, and/or that some featuresand/functions may be combined.

The term “portion” or “network portion,” or “portion of a network” asused herein may refer to a single device, a portion of a device (virtualdevice or partition), an application or group thereof, a plurality ofnetwork devices (including those grouped logically, physically, and/orgeographically), a service or group thereof provided by one or moredevices, a subnet, or other physical or logical division of a network.

Other embodiments, uses and advantages of the invention will be apparentto those skilled in the art from consideration of the specification andpractice of the invention disclosed herein. The specification should beconsidered exemplary only, and the scope of the invention is accordinglyintended to be limited only by the following claims.

1. A system for service assurance testing of a computer network,comprising: one or more processors configured to: receive networkinfrastructure information relating to the network, receive one or moreservice assurance testing parameters, determine a test schedule of oneor more service assurance tests for service assurance testing of thenetwork, the test schedule being based at least in part on the networkinfrastructure information, and the one or more service assurancetesting parameters, and deploy the one or more service assurance testson one or more devices of the network according to the test schedule. 2.The system of claim 1, wherein the network infrastructure informationincludes information relating to the physical topology of the network,and wherein at least one of the one or more service assurance tests aredevised based at least in part on a specific physical topology indicatedin the network infrastructure information.
 3. The system of claim 1,wherein the network infrastructure information includes traffic patterndata relating to traffic patterns within the network, and wherein atleast one of the one or more service assurance tests are devised basedat least on part on one or more specific traffic patterns from thetraffic pattern data.
 4. The system of claim 3, wherein the trafficpattern data includes at least data regarding data volume within one ormore specific portions of the network.
 5. The system of claim 4, whereinthe at least one of the one or more service assurance tests are devisedto be deployed to at least one specific portion of the network servicinga high volume of data.
 6. The system of claim 1, wherein the networkinfrastructure information includes traffic class information relatingto classification of traffic within the network, and wherein at leastone of the one or more service assurance tests are devised based atleast in part on a classification of traffic flowing to or from one ormore specific portions of the network.
 7. The system of claim 6, whereinthe classification of traffic is one of a plurality of classificationsrelating to traffic priority.
 8. The system of claim 7, wherein the atleast one of the one or more service assurance tests are directed to atleast one of the one or more specific portions of the network havingtraffic classified as high priority flowing thereto or therefrom.
 9. Thesystem of claim 1, wherein the network infrastructure informationincludes network technology information relating to one or more networktechnologies used at specific portions of the network, and wherein atlest one of the one or more service assurance tests are devised based atleast in part on a network technology of a specific portions of thenetwork from the network technology information.
 10. The system of claim9, wherein the one or more network technologies include one or more of:signaling technologies, propagation media, network standards, or networkprotocols.
 11. The system of claim 1, wherein the one or more serviceassurance testing parameters include one or more of: an indication ofone or more specific portions of the network to be tested using the oneor more service assurance tests, at least one test type, or a timingparameter deployment of the one or more service assurance tests
 12. Thesystem of claim 1, wherein the one or more service assurance testsinclude one or more of connectivity testing or performance testing. 13.The system of claim 1, wherein the one or more processors configured to:determine a test schedule of one or more service assurance tests furthercomprises one or more processors configured to: determine a cost of theone or more service assurance tests according to the one or morereceived service assurance testing parameters; and determine whether thecost is acceptable according to a predetermined standard.
 14. The systemof claim 13, wherein one or more processors configured to determinewhether the cost is acceptable according to a predetermined standardfurther comprise one or more processors configured to determine a testschedule of one or more service assurance tests according to alteredservice assurance testing parameters when it is determined that the costis unacceptable.
 15. The system of claim 1, wherein the one or moreprocessors are further configured to receive results of the one or moreservice assurance tests.
 16. The system of claim 15, wherein the one ormore processors are further configured to generate one or more reportsusing the received results.
 17. A method for service assurance testingof a computer network, the method being executed by one or moreprocessors configured to perform a plurality of operations comprising:receiving network infrastructure information relating to the network;receiving one or more service assurance testing parameters; determininga test schedule of one or more service assurance tests for serviceassurance testing of the network, the test schedule being based at leastin part on the network infrastructure information and the one or moreservice assurance testing parameters; and deploying the one or moreservice assurance tests on one or more devices of the network accordingto the test schedule.
 18. The method of claim 17, wherein the networkinfrastructure information includes information relating to the physicalstructure of the network, and wherein at least one of the one or moreservice assurance tests are devised based at least in part on a specificphysical structure indicated in the network infrastructure information.19. The method of claim 17, wherein the network infrastructureinformation includes traffic pattern data relating to traffic patternswithin the network, and wherein at least one of the one or more serviceassurance tests are devised based at least on part on one or morespecific traffic patterns from the traffic pattern data.
 20. The methodof claim 19, wherein the traffic pattern data includes at least dataregarding data volume within one or more specific portions of thenetwork.
 21. The method of claim 20, wherein the at least one of the oneor more service assurance tests are devised to be deployed tout leastone specific portion of the network servicing a high volume of data. 22.The method of claim 17, wherein the network infrastructure informationincludes traffic class information relating to classification of trafficwithin the network, and wherein at least one of the one or more serviceassurance tests are devised based at least in part on a classificationof traffic flowing to or from one or more specific portions of thenetwork.
 23. The method of claim 22, wherein the classification oftraffic is one of a plurality of classifications relating to trafficpriority.
 24. The method of claim 23, wherein the at least one of theone or more service assurance tests are directed to at least one of theone or more specific portions of the network having traffic classifiedas high priority flowing thereto or therefrom.
 25. The method of claim17, wherein the network infrastructure information includes networktechnology information relating to one or more network technologies usedat specific portions of the network, and wherein at lest one of the oneor more service assurance tests are devised based at least in part on anetwork technology of a specific portions of the network from thenetwork technology information.
 26. The method of claim 25, wherein theone or more network technologies include one or more of: signalingtechnologies, propagation media, network standards, or networkprotocols.
 27. The method of claim 17, wherein the one or more serviceassurance testing parameters include one or more of: an indication ofone or more specific portions of the network to be tested using the oneor more service assurance tests, at least one test type, or a timingparameter deployment of the one or more service assurance tests.
 28. Themethod of claim 17, wherein the one or more service assurance testsinclude one or more of connectivity testing or performance testing. 29.The method of claim 17, wherein determining a test schedule of one ormore service assurance tests further comprises: determining a cost ofthe one or more service assurance tests according to the one or morereceived service assurance testing parameters; and determining whetherthe cost is acceptable according to a predetermined standard.
 30. Themethod of claim 29, wherein determining whether the cost is acceptableaccording to a predetermined standard further comprises determining atest schedule of one or more service assurance tests according toaltered service assurance testing parameters when it is determined thatthe cost is unacceptable.
 31. The method of claim 17, wherein theoperations further comprise receiving results of the one or more serviceassurance tests.
 32. The method of claim 31, wherein the operationsfurther comprise generating one or more reports using the receivedresults.
 33. A system for service assurance testing of an computernetwork, comprising: one or more processors configured to: receivenetwork infrastructure information relating to the network, create a mapof at least a portion of the network, using the received networkinfrastructure information, wherein the map includes: informationrelating to the physical structure of the portion of the network,information relating to traffic within the portion of the network, andinformation relating to one or more services supported, at least inpart, by the portion of the network, receive one or more serviceassurance testing parameters, determine a test schedule of one or moreservice assurance tests for service assurance testing of the network,the test schedule being based at least in part on information includedin the map and the one or more service assurance testing parameters,deploy the one or more service assurance tests on one or more devices ofthe network according to the test schedule; receive results from one ormore of the deployed service assurance tests; and generate at least onereport based on the received results.